@christeredvartsen I just rebased this, so I think it's ready now.

The only functional change is in src/Exception/ArrayContainsComparatorException.php - where I changed the newlines. It's not the best, but it shouldn't be a breaking change seeing as it impacts exception messages (end users should never depend on the exact exception message).

The composer-cache-dir step seems to be problematic on windows:

- id: composer-cache-dir
  run: echo "dir=$(composer config cache-files-dir)" >> $GITHUB_OUTPUT

Also, since composer.lock is no longer committed, we might need to change this:

- id: composer-cache
  uses: actions/cache@v5
  with:
    path: ${{ steps.composer-cache-dir.outputs.dir }}
    key: ${{ runner.os }}-php-${{ matrix.php }}-composer-${{ hashFiles('**/composer.lock') }}

The remaining failures are most like because of newline mismatch. It will be clearer when I try it on my machine at home later on today.

The remaining failures are most like because of newline mismatch. It will be clearer when I try it on my machine at home later on today.

Sounds good. Perhaps some sort of normalization of newlines before matching might be an improvement?

I figured out the issue in a private repo.

PHP treats NOWDOC and other strings literally as they are in the source file, so if the source happened to contain garbage characters or CRLF, it keeps it as is.

The problem in this case is git's autocrlf setting that is somehow enabled on the github windows runner - when the files are checked out, git was replacing LF with CRLF (even if internally they were stored with LF).

A small change to .gitattributes should fix it for everyone.

The last remaining issue was about a dev-only requirement for ext-sockets, I solved it like I did for ext-fileinfo.

@christeredvartsen kind reminder - any chance of getting this merged in soon? I'd like to go further with some proposed changes depending on this one.